#!/bin/bash
set -euo pipefail

# 1) 检查 GCPoolCmd 在 Java 侧的构造与字段访问，确认是否仍有 volumes 依赖
rg -n -C3 --type=java '\bGCPoolCmd\b|\.whiteList\b|\.volumes\b'

# 2) 检查全仓库协议键使用，确认非 Java 端（例如脚本/agent）是否仍消费 "volumes"
rg -n -C2 "\"volumes\"|\"whiteList\"|'volumes'|'whiteList'"

# Read the GCPoolCmd class definition to see the full structure
sed -n '5231,5245p' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java

# Search for all usages of GCPoolCmd to see how it's being used
rg -n 'GCPoolCmd' --type=java -A 2 -B 2

# Check if there are any Python agent files that might reference "volumes" in GC context
find . -name "*.py" -o -name "*.sh" | xargs grep -l "volumes\|whiteList\|GCPool" 2>/dev/null | head -20

# Check the Python SDK backup file for any reference to GC or whiteList/volumes
cat testlib/src/main/resources/zssdk_bak.py | grep -i -C 5 "gc\|whitelist\|volumes" | head -50

# Search for GCPoolCmd instantiation and usage in Java code
rg -n 'new GCPoolCmd|GCPoolCmd\(' --type=java -A 5 -B 2

# Look for any agent-side code that handles protocol messages
find . -path "*/agent*" -name "*.py" | head -10

# Search for backwards compatibility patterns in the codebase (e.g., `@Deprecated` fields)
rg -n '@Deprecated' --type=java -B 2 -A 2 | head -50

# Search for where GCPoolCmd objects are created or serialized/deserialized
rg -n 'GCPoolCmd' --type=java -B 5 -A 10 | head -100

# Check if there's JSON serialization/deserialization of this command
rg -n 'whiteList|poolGc|gc.*cmd' -i --type=java | grep -i pool | head -20

# Look for any version compatibility or JSON field mapping annotations
rg -n '@JsonProperty|@SerializedName|@Deprecated' --type=java | grep -B 5 -A 5 'volumes\|whiteList' | head -50

# Search for KVM agent side code (if any Java-side marshalling happens)
find . -path "*kvm*" -name "*.py" | head -10

# Check git history to understand when this field was renamed and if volumes still exists in current branch
git log --oneline --all -- plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java | head -5

# Check the commit that renamed the field to understand the context
git show --stat 9099d7c08 | head -50

# Search for all references to 'volumes' in the KVM plugin context
rg -n 'volumes' plugin/kvm/src/main/java/org/zstack/kvm/ --type=java | head -30

# Look for where GCPoolCmd is instantiated or populated
rg -n 'GCPoolCmd\s*\(' -A 10 --type=java

# Check if agent code directory exists and has protocol definitions
find plugin/kvm -name "*agent*" -o -name "*protocol*" | head -20

# Search for any Java-to-agent communication code that might handle field mapping
rg -n 'toJson|fromJson|marshal|serialize' plugin/kvm/src/main/java/org/zstack/kvm/ --type=java | grep -i 'gc\|pool' | head -20

# Check the git diff of the commit that renamed the field
git show 9099d7c08 -- plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java | grep -A 20 -B 5 "GCPoolCmd"

# Check if volumes field was actually deleted or just renamed
git show 9099d7c08:plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java | sed -n '5231,5245p'

# Check the previous commit to see what the old field was
git show 9099d7c08^:plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java 2>/dev/null | sed -n '5231,5245p' || echo "Cannot retrieve previous version"

# Search for any code that creates GCPoolCmd to see if they've been updated
rg -n 'new GCPoolCmd|GCPoolCmd\s*\{\s*' -A 10 --type=java

# Check if there are integration tests or code generators that might handle the old field
rg -n '"volumes"|\.volumes' plugin/kvm/ --type=java | grep -i 'gc\|pool'

# Check if the file was tracked before this commit
git log --all --oneline -- plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java | head -10

# Check what branches have the old "volumes" field in GCPoolCmd
git branch -a --contains 9099d7c08^

# Search for where GCPoolCmd whiteList is being set or used
rg -n 'whiteList' plugin/kvm/ --type=java -B 3 -A 3

# Check if there's any code that populates GCPoolCmd with data
rg -n 'GCPoolCmd' plugin/kvm/src/main/java/org/zstack/kvm/ --type=java -B 10 -A 5 | head -100

# Look for the GC implementation to understand the context
rg -n 'class.*GC|gcPool|poolGc' plugin/kvm/ --type=java -i | head -20

# Check if whiteList is actually being used anywhere - setter or getter calls
rg -n 'whiteList|\.setWhiteList|\.getWhiteList' plugin/kvm/ --type=java -B 2 -A 2

# Look at GCPoolRsp to see if it mirrors the command
sed -n '5296,5310p' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java

# Search for where GCPoolCmd is being sent or received in the KVM Host class
rg -n 'GCPoolCmd\|gcPool' plugin/kvm/src/main/java/org/zstack/kvm/KVMHost.java -B 5 -A 5

# Check the commit before the current GCPoolCmd history to see old field name
git log --all --oneline -- "plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java" | tail -5

# Look for any `@JsonAnySetter` or custom deserialization that might handle backward compatibility
rg -n '@JsonAnySetter|@JsonDeserialize|@JsonProperty' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java -B 2 -A 2 | head -50

# Check AgentCommand class to understand `@JsonAnySetter` usage
rg -n 'class AgentCommand|@JsonAnySetter' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java -B 5 -A 10 | head -60

# Search for where GCPoolCmd is instantiated or populated
rg -n 'GCPoolCmd\s*\(\)|new GCPoolCmd' plugin/kvm/ --type=java -B 5 -A 10

# Look for code that sends GCPoolCmd to the agent
rg -n 'send.*GCPoolCmd|GCPoolCmd.*send' plugin/kvm/ --type=java -B 5 -A 5

# Check if there's an agent handler or any Python code that processes GCPoolCmd
find plugin/kvm -name "*.py" -exec grep -l "GCPool\|gc.*pool" {} \;

# Look at the test directory to see if there are integration tests for GCPoolCmd
find . -path "*/test*" -name "*.groovy" -o -name "*.java" | xargs grep -l "GCPool" 2>/dev/null | head -5

# Check what GrayUpgradeAgent does and if it provides backward compatibility
rg -n 'class GrayUpgradeAgent|@GrayVersion' core/src/ --type=java | head -30

# Look for GrayUpgradeAgent definition
find . -name "GrayUpgradeAgent.java" -o -name "GrayVersion.java" | head -5

# Check if `@GrayVersion` is used on GCPoolCmd or similar command classes
rg -n '@GrayVersion' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java -B 2 -A 2 | head -50

# Search for any backward compatibility patterns in the codebase related to field renaming
rg -n 'volumes.*whiteList|whiteList.*volumes' --type=java -B 5 -A 5

# Check if there's any documentation about the GC pool whitelist feature
rg -n 'ZSTAC-85164|85164' --type=groovy --type=java --type=java --type=md | head -20

# Read the GrayVersion and GrayUpgradeAgent classes to understand version compatibility
cat core/src/main/java/org/zstack/core/upgrade/GrayVersion.java

# Read the GrayUpgradeAgent class
cat core/src/main/java/org/zstack/core/upgrade/GrayUpgradeAgent.java

# Check if GCPoolCmd should have `@GrayVersion` annotation like other commands
sed -n '5230,5250p' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java

# Look for any code that actually uses GCPoolCmd - check if it's being set
rg -n 'GCPoolCmd|gcPool' plugin/kvm/src/main/java/org/zstack/kvm/ --type=java -B 3 -A 3

# Check if `@JsonAnySetter` exists on AgentCommand or AgentResponse for backward compatibility
rg -n 'public static class AgentResponse|@JsonAnySetter' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java -B 5 -A 15 | head -80

# Look for any JSON field mapping or compatibility converters
rg -n '@JsonProperty|@JsonAlias|fieldNameStrategy' plugin/kvm/src/main/java/org/zstack/kvm/ --type=java

# Check if there's a base class that handles JSON deserialization
rg -n 'class GrayUpgradeAgent' -A 50 core/src/main/java/org/zstack/core/upgrade/GrayUpgradeAgent.java

# Look for any deserialization test or agent protocol tests
find . -path "*/test*" -name "*.groovy" | xargs grep -l "GCPool\|whiteList" 2>/dev/null | head -5

# Check if GCPoolCmd field is actually used/serialized anywhere
rg -n 'whiteList\s*=' plugin/kvm/ --type=java -B 5 -A 5

# Look for any code that creates or populates GCPoolCmd
rg -n 'poolUuid|mountPoint|whiteList' plugin/kvm/src/main/java/org/zstack/kvm/KVMHost.java -B 3 -A 3

# Check if the commit was a complete file addition or if it modified an existing file
git show 9099d7c08 --name-status | grep KVMAgentCommands

# Verify if this is truly the first commit for this file or if there are older versions
git log --all --follow plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java --oneline

# Check if any agent code actually processes this command
find plugin/kvm -name "*.py" -exec cat {} \; | grep -i "gc\|pool" | head -20

# Look at the full commit to see if there were other files modified that might show the old implementation
git show 9099d7c08 --stat | grep -E "\.java|\.py"

# Check if there's any reference to the old "volumes" field in test files or agent code
find . -type f \( -name "*.py" -o -name "*.groovy" -o -name "*.java" \) -exec grep -l '"volumes".*pool\|pool.*"volumes"' {} \; 2>/dev/null | head -10

# Check if KVMAgentCommands.java is imported/used elsewhere
rg -n 'import.*KVMAgentCommands|GCPoolCmd' --type=java | head -20

# Check if `@GrayVersion` annotation was used on the whiteList field
sed -n '5220,5240p' plugin/kvm/src/main/java/org/zstack/kvm/KVMAgentCommands.java

# Verify if there are any older branches or tags with the old "volumes" field in GCPoolCmd
git branch -r --contains 9099d7c08 | head -5

# Check if there's any mention of the old field name in documentation or comments
rg -n 'volumes.*pool|pool.*volumes|GC.*retain|retain.*list' --type=java --type=groovy -i | grep -i 'gc\|pool' | head -20